Summary – What You Will Learn The benefits of moving from spreadsheets and manual tracking to real-time updates Field sales teams are constantly interacting with customers, distributors, contractors, and regional partners. These conversations often include important information such as pricing discussions, customer requirements, upcoming projects, and potential opportunities. However, in many manufacturing organizations, these interactions are not properly recorded. Information is often stored in notebooks, spreadsheets, or simply remembered by the salesperson. Over time, this creates a lack of visibility for managers and makes it difficult to understand what is happening across different territories. This blog explains how organizations can use Microsoft Dynamics 365 Sales to track field activities in a structured way and improve visibility into sales engagement and productivity. The Challenge The Field Sales Visibility Problem Field sales in manufacturing are highly relationship driven. Sales representatives regularly visit distributor branches, customer sites, and regional offices to maintain relationships and identify opportunities. But many of these interactions are never formally captured. This creates several challenges: a. No Interaction History Customer discussions and visit details are not recorded, making it difficult to track past conversations or commitments. b. Limited Visibility Across Teams Other team members and managers cannot easily see what has already been discussed with a customer. c. Difficulty Measuring Territory Engagement Managers may not know which territories are actively engaged and which areas need more attention. d. Missed Follow-Ups and Opportunities Potential opportunities discussed during visits may never be tracked properly in the sales pipeline. As a result, the CRM only reflects part of the sales activity, while many important field interactions remain invisible. The Solution Building a Structured Field Activity Process The goal is not to add extra administrative work for sales teams. Instead, the focus is on making activity tracking quick, simple, and useful. 1. Tracking Branch Visits and Customer Meetings Organizations can create a simple “Branch Visit” activity framework within the CRM to capture key field interactions such as: During each visit, sales teams can record useful details like: This helps create a consistent record of customer engagement across the organization. 2. Enabling Quick Mobile Updates Using the mobile capabilities of Microsoft Dynamics 365 Sales, sales teams can log activities directly from their phones immediately after meetings or visits. The process is simple and quick, helping improve CRM adoption without disrupting the sales team’s workflow. 3. Connecting Activities to Customers and Opportunities Recorded visits can be linked directly to customer accounts and ongoing opportunities. This allows teams to: 4. Turning Activities into Insights Once activities are consistently captured, organizations can generate useful reports such as: Customer Activity Reports These reports combine: into a single customer timeline, helping teams understand how frequently accounts are being engaged. Before vs after: what changes with a CRM The shift from manual tracking to structured CRM logging is less about technology and more about having one shared version of the truth. Area Without CRM tracking With CRM tracking Visit records Notebooks, memory, or nothing Logged on mobile, linked to the account Manager visibility Relies on what reps choose to share Real-time dashboard across all territories Team handovers Rep briefs colleague verbally, gaps guaranteed Full interaction history visible to the whole team Follow-ups Tracked in spreadsheets or not at all Tasks created in the CRM, assigned and time-stamped Territory review Guesswork or anecdote Activity reports per rep, per region, per account Salesperson Activity Reports These reports help managers: Using Microsoft Power BI, this information can also be displayed through dashboards for easier visibility and decision-making. Business Impact / Results When field activities are properly tracked, organizations gain much better visibility into their sales operations. Key benefits include: Managers can now: Most importantly, field sales productivity becomes visible, measurable, and easier to manage. For implementation within Microsoft Dynamics 365 Sales: These configurations help keep the process scalable while remaining easy for teams to use. FAQ Section a. What is a Branch Visit activity? A Branch Visit activity is a structured way to record field interactions such as distributor visits and customer meetings within the CRM. b. How does this improve productivity? It helps organizations track customer engagement more effectively and gives managers better visibility into sales activities. c. Can this data be visualized in dashboards? Yes. Using Microsoft Power BI, organizations can create dashboards to monitor territory activity and sales engagement. d. How can companies improve CRM adoption among field teams? Keeping the process simple, mobile-friendly, and quick to update encourages better adoption across sales teams. e. What changes for managers? Managers can focus on coaching and customer strategy instead of chasing updates. This also reduces time spent collecting updates manually and improves overall visibility into sales activities across regions. To conclude, Field sales will always depend on strong customer relationships. However, managing those relationships should not rely on memory, spreadsheets, or disconnected notes. By using Microsoft Dynamics 365 Sales to track and structure field activities, manufacturing organizations can gain better visibility into customer engagement and sales performance. Instead of guessing productivity, managers can rely on real-time data to understand how actively teams are engaging with customers and where improvements are needed. A structured field activity process helps organizations become more organized, more informed, and better prepared to manage sales growth. Connect with CloudFronts to get started at transform@cloudfonts.com Author Bio Cassandra Rodrigues is a D365 CRM Consultant specializing in CRM solutions and sales process optimization for manufacturing organizations. She focuses on helping businesses improve visibility, streamline operations, and build practical solutions using Microsoft Dynamics 365 Sales. If you’re looking to improve visibility into field sales activities and build a more structured, data-driven sales process, feel free to reach out to CloudFronts to learn how these solutions can be implemented within your organization.

Executive Summary Modern finance organizations operating in highly regulated, asset-intensive industries such as Oil & Gas and Marine Services face a growing paradox. While enterprise ERPs like Microsoft Dynamics 365 are designed to be systems of record, the surrounding financial ecosystem—banking portals, tax authority platforms, HR systems, and reporting tools—often remains fragmented and manually operated. This fragmentation introduces three systemic risks: This article presents a connected finance architecture where ERP, banking systems, and statutory compliance platforms are deeply integrated through APIs, transforming finance operations into a frictionless, auditable, and real-time engine. The solution described eliminates file-based handoffs, reduces human dependency, and establishes the ERP as a single source of financial truth. Industry Context: Why Energy & Marine Finance Is Uniquely Complex Organizations in the energy and marine sectors operate under conditions that magnify finance risk: In this environment, manual finance operations are not just inefficient—they are dangerous. Case Environment Overview The organization profiled in this implementation exhibits the following characteristics: Pre-Integration Challenges Before integration, finance operations were characterized by: These processes introduced latency, reconciliation gaps, audit exposure, and key-person dependency. The Core Problem: Disconnected Financial Workflows The central failure point was workflow discontinuity. Although financial transactions originated in the ERP, execution and compliance occurred outside it, breaking end-to-end traceability. Finance Stage System Used Risk Introduced Invoice Entry ERP Low Approval ERP Low Payment Execution Bank Portal High GST Filing GSP Portal High Reconciliation Excel Very High Every manual handoff created: The Vision: A Connected Finance Ecosystem The transformation goal was not automation for its own sake, but financial continuity. Design Principles Architecture Overview: ERP-Centric Integration Dynamics 365 Finance & Supply Chain was positioned as the financial command center. From this hub: This architecture eliminated spreadsheet dependency entirely. Regulatory Automation: Solving GST, E-Invoicing, and E-Way Bills The Compliance Challenge Manual GST compliance introduces risks such as: The Solution Integration with ClearTax enabled direct statutory interaction from Dynamics 365. Automated Capabilities Compliance ceased to be an external obligation and became a native ERP function. Automated Banking: From Approval to Disbursement Without Re-Entry The Payment Risk Manual bank instruction entry introduces: The Integrated Payment Flow This ensured zero data re-entry between ERP and bank. Governance Controls Embedded in the System 3-Way Matching Enforcement Mandatory matching between: This applies to both services and materials, ensuring no unauthorized leakage. N-Level Approval Framework Approval workflows span: Each approval is: HR Integration: Eliminating Expense Fragmentation HR expense data from Eazework flows directly into Dynamics 365. Benefits: Reconciliation and Audit Readiness A 1:1 relationship between bank accounts and main accounts was enforced. This resulted in: Decision Intelligence: Power BI as the CFO’s Cockpit Power BI dashboards provide: Dashboards refresh three times daily: Finance leaders operate on live data, not yesterday’s spreadsheets. Proof & Metrics Dimension Outcome Legal Entities 7 + 1 consolidation Compliance Scope GST, IRN, E-Way Bills Payment Modes NEFT, RTGS Manual Entry Eliminated Data Accuracy Single vendor master Reporting Latency Near real-time Step-by-Step Implementation Playbook FAQs a. Can E-Way Bills be cancelled from the ERP?Yes. Cancellation is automated and synchronized with the GST portal. b. How are On-Account payments handled?Payments can be created manually and auto-applied later without reconciliation issues. c. What happens to rejected vendors?They are auto purged after six months to maintain data hygiene. d. Closing Thought: Finance Without Friction The future of finance is not additional manpower-it is architectural integrity. Organizations that eliminate manual interfaces between ERP, banks, and regulators achieve: The frictionless finance engine is no longer optional. It is the new baseline. To conclude, for Oil & Gas and Marine service providers, financial complexity is not going away. Multi-entity structures, regulatory obligations, and high-value transactions will only intensify. The answer is not more people – it is better architecture. When ERP, banking, and compliance systems are genuinely connected, finance transforms from a cost center into a control center. Transactions execute without re-entry. Compliance happens within the workflow. Reconciliation closes itself. This implementation demonstrates that frictionless finance is not a future ambition – it is an available reality today. The only question left for finance leaders in this space is simple: How long can you afford to operate without it? Ready to Transform Your Finance Operations? If your organization is still bridging ERP, banking, and compliance through spreadsheets and manual processes, it is time for a different conversation. Our team has deep expertise implementing connected finance architectures for Oil & Gas and Marine service providers – from Dynamics 365 configuration to GST automation and real-time banking integration. Write to us at transform@cloudfronts.com and discover how quickly your finance function can move from fragmented to frictionless.

How We Built a Real-Time Lightweight Financial Statement Reporting Experience Directly Inside Microsoft Dynamics 365 Project Operations Summary Designed and deployed a lightweight, real-time financial statement reporting solution directly inside Microsoft Dynamics 365 Project Operations for a Texas-based Cybersecurity & AI Business Solutions firm. Eliminated dependency on heavy paginated reporting and large-scale Power BI datasets for operational financial visibility. Built an interactive HTML + JavaScript reporting framework embedded natively within Dynamics 365 CRM. Enabled dynamic filtering, instant report rendering, and printable customer-ready statements directly from the CRM interface. Introduced popup-based full-screen report rendering for detailed review and print-ready output without leaving Dynamics 365. Integrated funding balances, allocations, transactions, installment schedules, and financial snapshots into a single operational reporting experience. Reduced reporting development complexity, minimized data transformation overhead, and improved scalability compared to traditional BI-heavy architectures. Created a highly maintainable reporting model that scales efficiently as operational datasets grow without introducing significant Power BI licensing or performance constraints. Table of Contents Introduction The Business Problem The Solution Architecture Real-Time CRM-Native Reporting Lightweight Front-End Reporting Framework Popup-Based Printable Report Experience Data Model and Reporting Components Design Principles Business Impact Why This Approach Worked FAQs Conclusion 1. Introduction As organizations scale, operational reporting often becomes increasingly difficult to maintain. For a Texas-based Cybersecurity & AI Business Solutions firm operating on Microsoft Dynamics 365 Project Operations, this challenge became especially visible in financial agreement tracking and customer funding visibility. The business already had access to reporting platforms such as Power BI and paginated reports. However, these approaches introduced several operational problems: Long development cycles Heavy data-cleaning requirements Complex transformation pipelines Delayed visibility into operational data Increasing licensing costs as datasets expanded Slow report rendering for operational users Dependency on external reporting infrastructure Instead of another external BI layer, the organization wanted a lightweight operational reporting experience directly inside Dynamics 365 CRM itself. The Goal: Build a real-time, CRM-native financial reporting experience that renders instantly, supports dynamic filtering, enables printing, and scales without heavy BI infrastructure. 2. The Business Problem The organization manages multiple long-running service agreements, funding allocations, installment schedules, and customer financial balances across cybersecurity services, managed services, and AI solution engagements. Operational users needed a consolidated statement experience that could answer questions such as: What is the customer’s current available balance? Which transactions impacted the balance during a selected period? Which allocations are currently active? How much funding has been consumed vs allocated? Which installments are pending, paid, or overdue? What does the latest funding snapshot look like? Can the report be reviewed and printed directly from CRM? Paginated Reporting Limitations Increasing query complexity Performance degradation with larger datasets Heavy formatting maintenance Limited interactivity Rigid deployment cycles Power BI Challenges Significant Power Query transformations Data-cleaning pipelines Incremental refresh considerations Dataset refresh latency Licensing growth with scale Overengineering for transactional operational reporting 3. The Solution Architecture The reporting framework was designed as a native Dynamics 365 embedded reporting experience using: HTML Web Resources JavaScript Dynamics 365 Web API Native CRM navigation APIs Real-time entity retrieval Popup-based print rendering Embedded Operational Report Apply filters Select funding records Choose reporting periods Generate statements instantly Navigate operational financial data Popup Print Report Detailed review Executive presentation Customer-facing statements Printing and PDF generation 4. Real-Time CRM-Native Reporting One of the most important architectural decisions was avoiding external data replication entirely. Instead of pushing transactional data into a separate reporting warehouse, the report retrieved data directly from Dynamics 365 using the native Web API. Real-time visibility Zero synchronization lag Reduced infrastructure complexity Lower maintenance overhead Faster deployment cycles Everything rendered on demand inside the CRM session itself. 5. Lightweight Front-End Reporting Framework The reporting experience was intentionally designed to behave more like a modern application than a traditional report. Dynamic Filter Bar Users could dynamically filter reports using: This Month Last Month This Quarter Current Year Custom Date Ranges Funding Status Funding Selection The report regenerated instantly without page reloads. Responsive Report Rendering The reporting layout dynamically populated: Account Summary Transaction Details Allocation Summary Installment Details Detailed Account Summary Each section rendered independently based on live API responses. Intelligent Empty-State Handling Instead of showing blank tables or errors, the framework displayed contextual empty-state messaging such as: “No transactions during this statement period” “No active allocations” “No installment details available” This significantly improved usability for operational teams. 6. Popup-Based Printable Report Experience A major requirement was enabling users to thoroughly review and print reports directly from CRM. To solve this, the solution introduced a dedicated popup rendering architecture. Users could click: “Expand Report” This launched a fullscreen popup using Dynamics 365 navigation APIs with: Large-format rendering Print-optimized layout Full customer statement formatting Multi-page support Consistent branding Printable tables Customer reference guides The popup approach delivered several advantages: Better readability Cleaner print formatting Improved executive review experience Isolation from CRM form clutter Easier PDF generation Most importantly, the popup still worked entirely against live CRM data. 7. Data Model and Reporting Components The report consolidated multiple operational areas into a single experience. Account Summary Provided a high-level balance overview including: Balance Forward Total Credits Total Debits Closing Balance This gave immediate visibility into customer financial standing. Transaction Details Displayed detailed running balance activity including: Document date Transaction description Service type Credits Debits Running balance Transactions dynamically recalculated balances during rendering. Allocation Summary Tracked funding allocation activity including: Allocated funds Consumed funds Remaining balance Allocation status Returned allocations were handled separately with custom date logic. Installment Tracking Displayed installment lifecycle visibility including: Invoice dates Due dates Payment dates Payment terms Installment status The report intelligently handled future-dated payments and pending statuses. Detailed Funding Snapshot Displayed operational funding metrics including: Starting Balance Contracted Funds Total Budgeted Funds Collected Funds Used Funding Available Funds Allocated Funds Unallocated Funds This created a complete operational funding overview within a single screen. 8. Design Principles Several architectural principles guided the solution. Real-Time Over Batch Processing Operational reporting should reflect current business activity immediately. The solution avoided overnight refresh cycles entirely. Lightweight Over Heavy BI Not … Continue reading How We Built a Real-Time Lightweight Financial Statement Reporting Experience Directly Inside D365 PO for a Texas-Based Cybersecurity Firm →

Global energy service providers operate across multiple jurisdictions, currencies, and regulatory regimes. This complexity demands precision in financial reporting and transparency in profitability analysis. Achieving reliable site-level profitability in such an environment requires a holistic architectural approach to financial consolidation rather than incremental fixes or tactical workarounds. Legacy State Challenges Strategic DecisionThe organization implemented Dynamics 365 Finance & Supply Chain as a unified financial backbone, replacing legacy IFS systems and spreadsheet-driven workflows. This decision was accompanied by a critical architectural trade-off: moving away from locally customized, entity-specific account structures toward a single, global Chart of Accounts (COA). Benefits of Standardization Unified COA StructureThe global COA was standardized using a 1000–6000 series: This created a common financial language across the organization, enabling both global consolidation and local statutory compliance. Engineering Derived Dimensions for Data Integrity Standardizing accounts alone was insufficient to achieve granular profitability visibility. The architecture required a mechanism to enforce dimensional consistency and eliminate manual errors. Derived Dimension FrameworkFive core dimensions were defined: Segment, Sub-Segment, Region, State, and Site. System Integration Operational Customization From Static Spreadsheets to Dynamic Power BI Dashboards Legacy Reporting Modernized Workflow Reporting Model Operational Cadence Frameworks Proof and Metrics Step-by-Step Implementation Playbook FAQs a. How do you handle different fiscal years?The system supports reporting for both January–December and April–March fiscal calendars to meet diverse statutory requirements. b. Can we track unbilled revenue?Yes. Project Management modules track planned versus actual work, allowing finance teams to post and reverse accrued revenue monthly. c. What happens if a site selects the wrong dimension?This risk is mitigated through derived dimensions, which automatically populate dependent dimensions based on the selected Site code. To conclude, this architecture not only addresses immediate challenges but also positions the organization for long-term sustainability. It enables leadership to make informed decisions based on reliable, timely data, while ensuring compliance across diverse regulatory environments. Ultimately, the shift represents a move from reactive financial management to proactive, strategic control-delivering clarity, accountability, and resilience across global operations. Connect with CloudFronts to get started at transform@cloudfonts.com

Building a Controlled Booking-to-Time Entry Import Framework Inside Dynamics 365 Project Operations Summary Two Texas-based firms — one in Cybersecurity, another in Operational Security — required a streamlined and controlled Time Entry (TE) creation process inside Dynamics 365 Project Operations. Native D365 Project Operations limitations around Project Task visibility, booking-driven TE creation, and inconsistent resource submissions created operational inefficiencies. A fully customized solution was implemented directly inside Dynamics 365 CRM using HTML Web Resources, JavaScript, Dataverse Web API, Ribbon Enable Rules, and custom plugins. The solution centralized TE creation under Project Managers and Project Approvers, enabling controlled and secure booking-based TE management. A custom booking import framework dynamically surfaced only authorized projects and resources based on Project Approver relationships. Custom plugin logic and Resource Assignment–based task resolution automated Project Task mapping for accurate Time Entry creation. Key capabilities delivered included controlled booking imports, role-based visibility, automated task association, external comments support, and bulk TE creation. Dynamic filtering ensured Project Managers could only access resources and bookings associated with projects they were authorized to manage. The entire experience operated natively inside Dynamics 365 Project Operations without external portals, Power Apps screens, or third-party applications. The implementation reduced manual effort, improved TE submission reliability, increased operational flexibility, and enabled more accurate tracking of actual project work. Table of Contents Introduction The Business Problem & Pain Points The Solution Architecture Implementation Design Principles Business Impact Why This Approach Worked FAQs Conclusion 1 Introduction Two Texas-based firms operating in the Cybersecurity and Operational Security space relied heavily on Dynamics 365 Project Operations for project delivery tracking, resource management, and operational execution. As project operations scaled, Project Managers and Project Approvers required a faster and more controlled mechanism for creating Time Entries (TEs) directly from resource bookings. The organizations needed a solution that could simplify booking imports, improve Project Task mapping, enforce role-based visibility, and reduce the dependency on individual resources for manual TE submissions. Operationally, Project Managers were often responsible for validating and entering actual work performed, making the standard TE process inefficient and time-consuming. Key Challenges Standard Dynamics 365 Project Operations behavior did not fully support project-task-aware Time Entry creation from bookings. Project Task values were not consistently available across Resource Requirements and bookings in several PO environments. Resource-driven TE submission resulted in inconsistent and delayed operational reporting. Project Managers lacked centralized visibility and controlled access to resource bookings across approved projects. Native booking import and TE creation workflows lacked flexibility for operational governance and scalability. Goals of the Solution Centralize Time Entry creation under Project Managers and Project Approvers. Enable controlled booking imports with role-based project visibility. Automate Project Task association during TE creation. Allow bulk creation of booking-driven Time Entries directly inside CRM. Improve operational accuracy, flexibility, and governance without relying on external applications or custom portals. 2 The Business Problem & Pain Points 1. Native Booking-to-Time Entry Limitations Standard Dynamics 365 Project Operations behavior did not consistently expose Project Task information through Resource Requirements and Bookings. This created gaps in task-aware Time Entry creation and forced users to manually reconstruct operational context during the TE process. 2. Lack of Controlled Booking Visibility Default system behavior provided broader booking visibility than operationally required. The organizations needed a controlled access model where only designated Project Managers and Project Approvers could view and manage booking imports for authorized projects. 3. High Manual Effort in Time Entry Creation Project Managers and operational teams spent significant time manually entering project references, tasks, durations, and external comments for each Time Entry. This increased administrative overhead and reduced operational efficiency. 4. Inconsistent Resource-Driven Submission Process The organizations faced reliability challenges with resource-submitted Time Entries, leading to delays, missing entries, and inconsistencies in operational reporting. Project Managers required centralized ownership over TE creation to ensure accurate work tracking. 5. Fragmented User Experience Users were required to navigate across multiple Dynamics 365 screens and entities to complete routine booking import and Time Entry operations, making the process cumbersome and inefficient for daily operational usage. 6. Scalability and Maintainability Concerns The firms required a lightweight and scalable solution that could operate natively within Dynamics 365 Project Operations without introducing unnecessary Power Apps layers, external portals, or high-maintenance custom applications. 3 The Solution Architecture Architecture Diagram and Flow Figure: Complete Frontend – Backend behaviour of the TE Automation Module. Dynamics 365 Ribbon Workbench A custom “Import Resource Bookings” ribbon action was introduced to provide controlled access to the booking import process only for authorized Project Managers and Project Approvers. JavaScript + Dataverse Web API JavaScript and Dataverse Web API were used to handle dynamic project filtering, approver validation, booking retrieval, task mapping, and automated Time Entry creation directly inside CRM. HTML Web Resources Two custom HTML-based interfaces were developed: Resource Selection Interface — controlled resource visibility and selection Booking Import & TE Creation Interface — booking imports, task selection, external comments, and bulk Time Entry creation Dataverse Plugin Layer A lightweight custom C# plugin was implemented to support Project Task resolution, task validation, and booking-to-Time Entry automation scenarios not fully supported natively in Dynamics 365 Project Operations. Dataverse Entities Involved The solution leveraged multiple Project Operations entities: msdyn_project msdyn_projectteam msdyn_resourceassignment msdyn_projecttask bookableresource msdyn_resourcerequirement bookableresourcebooking msdyn_timeentry Together, these entities enabled secure, project-aware, and task-aware operational workflows directly inside Dynamics 365 CRM. Entity Relationships Figure: Relationships and associations of the involved entities. 4 Implementation 1. Role-Controlled Ribbon Visibility A custom ribbon action was implemented to ensure only authorized Project Managers and Project Approvers could access the booking import functionality. Visibility was dynamically controlled based on project approval relationships inside Dynamics 365. Figure: Case 1: When Logged in as a Project Approver/Manager. Figure: Case 2: When NOT Logged in as a Project Approver/Manager. 2. Resource Selection Experience A custom resource selection interface was developed to display only eligible resources associated with projects managed by the logged-in approver. This provided secure and simplified operational visibility. Figure: Bookable Resource Selection from a list of Active Bookable Resources, which are under any Project, where the current … Continue reading Building a Controlled Booking-to-Time Entry Import Framework Inside Dynamics 365 Project Operations for Texas-Based Operational Security & Cybersecurity Firms →

  Summary A custom steel windows and doors manufacturer had complex shop floor stages tracked entirely by hand, with no system connecting the sales office to production. CloudFronts developed a custom Order Fulfillment module within Dynamics 365 Sales and implemented trigger-based Power Automate flows to automate over 60 internal and external email communications across every stage of production. Microsoft recommends Power Automate cloud flows as the modern path forward over classic workflows, which receive limited ongoing investment. These were fully migrated, restoring consistent and professional client communication. The sales commitment now automatically extends into every production stage — from Preprocessing Order through Engineering & Calculations all the way to Scheduling Arrangements — without any manual follow-up from staff. Table of Contents   1. Customer Scenario 2. The Real Problem 3. Solution Overview 4. Key Components of the Solution 5. How It Works: Technical Implementation 6. End-to-End Walkthrough 7. Architecture and Design Decisions 8. Business Impact 9. FAQs 10. Conclusion Customer Scenario A manufacturer of custom steel windows and doors uses Dynamics 365 Sales to manage its customer relationships and order pipeline. The business builds bespoke, high-specification products where every order is unique, every unit requires individual engineering, and every delivery carries a direct reputational commitment to the client. The production journey for each order moves through a structured Business Process Flow (BPF) with the following discrete stages: Preprocessing Order: Initial order intake, validation, and readiness checks before the order enters the formal workflow Order Details: Full capture of specifications, dimensions, materials, and client requirements against the order record Assign Project Manager: A project manager is designated and formally takes ownership of the order in Dynamics 365 Project Manager: The assigned PM reviews the order, aligns with the client if required, and confirms the production brief Engineering & Calculations: Structural and thermal specifications are drawn up; shop drawings are prepared and sent for customer approval Production Review: Internal sign-off before the order enters active fabrication In Production: Active manufacturing — covering CNC machining, welding, painting, finishing, and quality control as sub-activities within this stage Quality Control: Final inspection against specification before dispatch clearance is issued Scheduling Arrangements: Protective packaging, carrier coordination, dispatch scheduling, and delivery confirmation Each stage involves different teams, different external parties, and different communication requirements. All of this was being managed entirely by hand. The Real Problem The organisation’s CRM and manufacturing operations existed in two separate worlds. A deal won in the sales office would trigger a handoff to the shop floor, but from that point the CRM had no visibility into what happened next. Production moved forward, but the system of record did not. This disconnect created three compounding problems: 1. Manual Tracking Across Nine BPF Stages With nine distinct BPF stages per order — from Preprocessing Order through to Scheduling Arrangements — and dozens of active orders at any given time, tracking which orders were where and who needed to be notified was a full-time administrative burden. Teams relied on printouts, spreadsheets, and internal messaging. The risk of an order falling through the cracks was constant. 2. Over 60 Email Templates Managed by Hand Customer-facing and internal communications spanned more than 60 distinct email templates covering stage transition notifications, drawing approvals, production confirmations, and dispatch alerts. Each one required a staff member to remember when to send it, select the right template, fill in the correct order details, and copy the right recipients. A missed email left a customer without an update. A wrong email required a correction and an apology. 3. Legacy Classic Workflows Limiting Reliability Some automation had been attempted through Dynamics 365’s classic workflow engine. Microsoft has been steering organisations toward Power Automate cloud flows as their modern, actively invested automation platform — classic workflows have not kept pace in terms of investment or feature development. Beyond this strategic direction, the existing classic workflows had become fragile over time: triggering at the wrong time, failing silently, or firing duplicate emails when conditions were partially met. The team had lost confidence in the automation and was increasingly bypassing it, falling back to manual processes. The system was not broken in any single dramatic way. It was failing in dozens of small ways, every day, and the cumulative cost showed up in staff time, customer experience, and operational risk. ⚠ Manual Tracking 9 BPF stages per order Dozens of active orders Printouts and spreadsheets No real-time visibility Orders falling through gaps ⚠ 60+ Email Templates All managed by hand Wrong template = apology Missed email = unhappy client No standardisation High staff cognitive load ⚠ Legacy Classic Workflows Microsoft recommends moving to Power Automate Limited ongoing investment in classic workflows Duplicate emails firing Silent failures Team bypassing automation Figure 2: The three core pain points driving the need for change Solution Overview CloudFronts addressed each pain point with a targeted, interconnected solution built on the existing Dynamics 365 platform. No third-party systems, no new infrastructure, and no disruption to the tools the team already knew. Custom Order Fulfillment Module in Dynamics 365  +  Trigger-Based Power Automate Cloud Flows  +  Full Migration from Legacy Classic Workflows   For the Production Team: Every order’s BPF stage — from Preprocessing Order to Scheduling Arrangements — is tracked directly within Dynamics 365, visible to sales, operations, and management in real time Stage transitions automatically trigger the correct notification with no manual action required Engineering & Calculations, Production Review, Quality Control, and Scheduling Arrangements are managed as structured fields rather than informal notes or emails For the Sales Team: The CRM record now follows the order all the way to delivery. The sale does not end at contract signature Customer-facing communications are consistent, professionally formatted, and sent automatically No more chasing production teams for status updates to relay to clients For the Organisation: A single source of truth for every order, from first contact through final dispatch Reliable, Microsoft-supported Power Automate automation that can be trusted rather than worked around A professional communication experience that reflects the quality … Continue reading From Manual Emails to Power Automate Cloud flows: Connecting Dynamics 365 Sales to the Shop Floor →

Summary Designed a two-page Power BI Income Pipeline Report for a Texas-based Cybersecurity & AI Business Solutions firm using Microsoft Dynamics 365 Project Operations. Unified visibility across Opportunity, Unbilled Income, Billed Income, and Paid Income in a single view. Introduced Average Turnaround to forecast realistic cash collection timelines based on actual payment behavior. Integrated Dynamics 365 Project Operations with QuickBooks to connect sales, delivery, invoicing, and cash collection. Enabled a 17-week rolling revenue forecast with week-by-week cash visibility. Provided dual invoice status for contractual vs realistic payment tracking. Table of Contents 1. Introduction 2. The Business Problem 3. Report Structure Overview 4. The Income Pipeline 5. Project Revenue Forecast 6. Design Principles 7. Business Impact 8. FAQs 9. Conclusion 1. Introduction Managing revenue across a professional services firm is rarely straightforward. When your business spans cybersecurity assessments, AI-driven solutions, and long-term managed services engagements, the gap between work being delivered and cash actually landing in the bank can be wide — and costly if left unmonitored. This is precisely the challenge we set out to solve for a U.S.-based Cybersecurity and AI Business Solutions firm running their operations on Microsoft Dynamics 365 Project Operations. The result was a two-page Power BI report — the Income Pipeline Report — that gives leadership a real-time, end-to-end view of every dollar moving through the business: from early-stage opportunity, through unbilled and billed income, all the way to cash collected. This post walks through how the report was built, how each data layer was modelled, and why the design decisions were made the way they were. 2. The Business Problem The firm needed clarity across four distinct but connected stages of their revenue lifecycle: Sales opportunities and pipeline value Delivered but unbilled work Outstanding invoices and expected payments Actual vs expected payment behavior This would answer as well as resolve the following questions – Where are active sales opportunities sitting, and how much pipeline value do they represent? Which project work has been delivered but not yet invoiced? Which invoices have been raised and sent to clients, and when are they realistically going to be paid? And finally, how does actual payment behaviour compare against what was expected? Each of these questions existed in isolation before. Project managers had partial visibility into their own contracts, and needed a comprehensive bird’s eye view of all of these together. Finance had QuickBooks data but lacked the context of the delivery pipeline. Leadership had no consolidated view. The Income Pipeline Report brought all of this together in a single, navigable Power BI experience. 3. Report Structure Overview The report consists of two pages: Income Pipeline Report — a high-level pipeline view across four stages: Opportunity, Unbilled Income, Billed Income, and Paid Income, each with summary cards and interactive donut charts. Project Revenue Forecast — a time-distributed breakdown of expected cash collection across a rolling 17-week horizon, organised by customer and contract. 4. The Income Pipeline The Four-Stage Pipeline Banner Across the top of the report, four chevron-style stage indicators guide the revenue journey: Opportunity → Unbilled Income → Billed Income → Paid Income Each stage includes a summary card showing record count and total value Provides immediate visibility into where revenue is sitting Highlights potential bottlenecks across the pipeline Stage 1 — Opportunity Data sourced from Dynamics 365 Sales using Business Process Flow (BPF) Uses active BPF stage (Develop, Propose, Close) instead of static fields Ensures accurate reflection of real sales progression Estimated revenue pulled directly from opportunity records Donut chart shows distribution across Develop, Propose, and Close stages Stage 2 — Unbilled Income Represents contracted or delivered work not yet invoiced Sourced from project contract lines in Dynamics 365 Project Operations Includes: Fixed Fee milestones (explicit values) Time & Material (T&M) estimates based on resource allocations T&M calculated as allocated hours × billing rate Clearly marked as estimated until billing run is executed Grouped into payment expectation buckets (30, 60, 90, 120, 180+ days) Uses Average Turnaround to forecast realistic payment timing Stage 3 — Billed Income (Confirmed Invoices) Combines Dynamics 365 Project Operations and QuickBooks data Tracks invoices that are confirmed and sent to clients Introduces Average Turnaround: Average days from invoice creation to payment Based on historical payment behaviour Each invoice has two statuses: Contractual (due date) Estimated (based on Average Turnaround) Provides realistic vs contractual payment visibility Includes: Due-date based categorisation Estimated overdue analysis Prevents misleading insights from strict payment terms alone Stage 4 — Paid Income Tracks fully collected invoices Uses QuickBooks for actual payment dates Groups payments by time bands (under 30, 60, 90 days, etc.) Enables comparison between actual vs estimated payment behaviour Continuously improves accuracy of Average Turnaround Tooltip Drill-Down Hover shows: Payment band Record count Total value Drill-through available for detailed record-level analysis 5. Project Revenue Forecast Overview Distributes expected cash collection across a rolling 17-week window Shifts view from pipeline stage to time-based forecasting Hierarchy and Structure Customer → Contract → Revenue Type Revenue types include: T&M run schedules Fixed Fee milestones Confirmed invoices Each row shows: Customer Contract Billing type Average Turnaround Value mapped to expected payment week Weeks range from Week 0 to Week 16 Top row aggregates total expected cash per week Colour Coding Amber — Unbilled income Green — Invoice within terms Red — Overdue (based on estimated payment date) Drill-Through to Detail Click any row to view detailed breakdown Includes: Billed invoices with due and estimated dates Unbilled milestones and run schedules Connects high-level forecast to transactional detail 6. Design Principles Average Turnaround over payment terms Reflects actual customer behaviour instead of contractual assumptions. Dual invoice status Provides both contractual and realistic payment visibility. Consistent time buckets Ensures comparability across Opportunity, Unbilled, Billed, and Paid stages. Weekly forecasting instead of monthly Supports short-term cash flow planning aligned with operational rhythm. 7. Business Impact Improved cash flow predictability Earlier visibility of at-risk invoices Unified cross-team visibility Improved T&M billing discipline Increased accountability 8. FAQs What is Average Turnaround and why does it … Continue reading How we designed & deployed an Income Pipeline Report for a Texas, U.S. based Cybersecurity & AI Business Solutions Firm, via MS D365 Project Operations and Power BI. →

In Microsoft Dynamics 365 Finance & Operations, direct SQL access to Sandbox environments is restricted for security reasons. However, you can access the Sandbox database from a DEV VM using Just-in-Time (JIT) access and SQL credentials provided through Lifecycle Services (LCS). This guide explains the complete process step-by-step. Prerequisites Before connecting, ensure you have: Step 1: Request JIT Access Open your Sandbox environment in LCS. Navigate to: Environment → Maintain → Enable access Depending on organization policies: Common access types: Step 2: Retrieve SQL Connection Details After JIT access is enabled: Go to: Environment Details → Full details You will find: Example: Field Example Server axdbserver.database.windows.net Database AxDB Authentication SQL Authentication Step 3: Whitelist DEV VM Public IP (If Required) Some environments require firewall whitelisting. From DEV VM: In LCS: Maintain → SQL firewall configuration Add: Wait a few minutes for propagation. Step 4: Open SSMS on DEV VM Launch: SQL Server Management Studio Step 5: Enter Connection Details In SSMS: Server Name Paste SQL server name from LCS. Example: axdbserver.database.windows.net Authentication Select: SQL Server Authentication Login Enter SQL username from LCS. Password Enter temporary password from LCS. Step 6: Configure Encryption Settings Click: Options → Connection Properties Ensure: Step 7: Connect to Database Click: Connect If successful, you can access: Important Notes Sandbox Databases Are Usually Read-Only Microsoft restricts many write operations. Avoid: unless explicitly approved. Access Is Temporary JIT access expires automatically after the approved duration. You may need to: Production Database Access Direct Production DB access is heavily restricted and generally unavailable. Use: instead. Common Connection Errors Login Failed Possible reasons: Cannot Open Server Requested by Login Usually firewall issue. Solution: SSL / Certificate Error Enable: Recommended Best Practices Use Read-Only Queries Prefer: SELECT TOP 100 * FROM CUSTTABLE Avoid update/delete statements. Use Views Instead of Base Tables Many standard views provide safer reporting access. Avoid Heavy Queries Large queries may impact environment performance. Example SQL Query SELECT TOP 10 ACCOUNTNUM, NAME FROM CUSTTABLE ORDER BY CREATEDDATETIME DESC Security Recommendations To conclude, Using Just-in-Time (JIT) access to connect a Sandbox database through SQL Server Management Studio (SSMS) in Microsoft Dynamics 365 Finance & Operations provides a secure and controlled way to troubleshoot, validate data, and perform reporting activities without granting permanent elevated access. Reach out at transform@cloudfronts.com.

Summary: In industrial manufacturing, especially in sectors like piping systems, fittings, and castings, the sales process is not a simple transaction, it is a structured, multi-stage bid lifecycle. This blog explains how organizations can manage the entire journey from lead generation to project completion using Dynamics 365 Sales. It also highlights how organizations can: Industrial sales in manufacturing industries such as pipes, fittings, and castings involve long sales cycles, multiple stakeholders, and highly detailed technical and commercial evaluations. Unlike standard product sales, these deals often begin with tenders or RFQs and require coordination across sales, engineering, finance, and production teams. Without a structured system, it becomes difficult to track bid progress, maintain version control, and ensure timely responses. This is where Dynamics 365 Sales plays a crucial role. It provides a centralized platform to manage every stage of the industrial bid process, ensuring visibility, accountability, and efficiency. From capturing initial leads to closing deals and delivering projects, it helps organizations streamline operations and improve win rates. The Challenge Section The Problem with Disconnected Data Organizations often manage sales and bid-related data across multiple systems such as ConstructConnect, Excel sheets, and offline trackers. This creates several operational challenges: As a result, the bidding process becomes reactive instead of proactive, slowing down execution and reducing win probability. Manufacturing companies dealing with industrial products face several challenges during the bid process: These challenges can result in missed opportunities, delayed submissions, and reduced customer confidence. The Solution Section Building a Structured Lead-to-Project Pipeline A key improvement is bringing all activities into a centralized system like Dynamics 365 Sales. Some practical steps include: Projects can then follow a clearly defined lifecycle: This structured pipeline ensures: Enforcing Pipeline Discipline and Accountability One key insight from mature implementations is the importance of pipeline governance. This includes: For example: This brings accountability and keeps the pipeline active and realistic. Improving Quote Tracking and Automation Quote management becomes significantly more efficient with automation. Key capabilities include: This ensures: Enhancing Visibility for Decision Making With all data centralized, leadership gains meaningful insights into the sales pipeline. Examples include: This enables: Business Impact / Results Section Adopting a unified system like Dynamics 365 Sales leads to tangible improvements: Result:A centralized platform replaces fragmented tools, enabling organizations to manage bids more effectively and improve overall project outcomes. With automation across lead capture, pipeline tracking, quote management, and follow-ups, up to 80% of the bid-to-project lifecycle can be automated, significantly reducing manual effort and operational delays. Technical Deep-Dive For organizations requiring deeper customization: FAQ Section Q1. Why is a single system important for managing industrial bids?A single system eliminates data silos, reduces manual work, and ensures all teams work with the same, up-to-date information. This improves coordination and increases the chances of winning bids. Q2. How does Dynamics 365 Sales support the industrial bidding process?It provides a structured pipeline, tracks projects from lead to completion, enables collaboration across teams, and automates key activities such as quote management and follow-ups. Q3. Can we customize the sales stages to match our business process?Yes, stages like Opportunity can be renamed to “Project,” and custom stages such as Pre-Qualified, Submittal, Negotiation, and Commitment can be configured to reflect the actual industrial bidding lifecycle. Q4. How does the system help in identifying projects at risk?Projects with no recent activity or delays in stage movement can be automatically flagged, allowing teams to take timely action and prevent potential losses. Q5. What improvements can be expected after implementation?Organizations typically see better data accuracy, faster bid processing, improved team accountability, and enhanced visibility into the sales pipeline. Q6. Can Dynamics 365 integrate with tools like ConstructConnect?Yes, it can integrate with external platforms to automatically import leads and project data, reducing manual entry and ensuring consistency. Q7. How much of the bid process can be automated using Dynamics 365 Sales?A significant portion of the process can be automated, including lead capture, stage tracking, quote handling, reminders, and reporting. In well-structured implementations, up to 80% of the bid-to-project lifecycle can be automated, allowing teams to focus on strategic and high-value activities. Conclusion Managing industrial bids across disconnected tools creates inefficiencies that directly impact business performance. By transitioning to a unified system like Dynamics 365 Sales, organizations can standardize their processes, automate critical tasks, and gain complete visibility into their pipeline. From capturing leads to delivering completed projects, a structured and integrated approach ensures better control, faster execution, and improved success rates. If your organization is still managing bids through spreadsheets and multiple systems, it may be time to move towards a more structured, scalable solution with Dynamics 365 Sales. Connect with CloudFronts to get started at transform@cloudfonts.com Author Bio The author specializes in implementing Dynamics 365 solutions for manufacturing and industrial sectors. With experience in optimizing sales processes, bid management, and system integrations, they focus on helping organizations streamline operations and improve efficiency through digital transformation.

What happens when a global manufacturing giant needs to modernize its operations without grinding critical business processes to a halt? The answer is not a rip-and-replace approach – it is a carefully engineered integration strategy that lets modern and legacy systems co-exist, communicate, and complement each other. Are you planning an ERP upgrade but worried about what happens to the legacy systems your operations depend on? If so, this is for you. One of North America’s leading commercial vehicle manufacturers faced exactly this dilemma. With decades of investment in legacy financial and warehouse management systems, a hard cutover to a new ERP was not an option. Yet the need for a modern, scalable platform was undeniable. Their solution? Introduce Microsoft Dynamics 365 Finance & Operations (D365 F&O) as the new operational backbone – while keeping their legacy systems in play for financial control – and build robust, bi-directional integrations to bridge both worlds. At CloudFronts, we had the privilege of architecting and implementing those integrations. This blog walks you through three core data flows: Spot Purchase Orders, Advance Shipment Notices (ASN), and Goods Receipt Notes (GRN) – and what it really takes to make a modern ERP talk to a legacy system without missing a beat. Why Replace When You Can Integrate? Legacy systems in large manufacturers are not just old software. They carry years of financial logic, vendor relationships, and compliance configurations that are too risky to discard overnight. Replacing them introduces enormous operational and compliance risk. Doing nothing, however, is not an option either. The approach our client took – and one we increasingly recommend for manufacturers, distributors, and large enterprises – is a co-existence model: This means the business gets the agility of a modern ERP on day one, without putting financial operations at risk. The three integrations do the heavy lifting. Architecture at a Glance Before diving into each integration, it helps to understand the overall data flow pattern and the Azure services involved: Component Role D365 F&O System of record for purchasing and receiving operations Legacy System Retains financial control, inventory management authority Azure Logic Apps Parent-child middleware: orchestrates, transforms, and routes data Azure Blob Storage Checkpoint management for reliable incremental processing Azure Table Storage Full execution logs for traceability, audit, and failure replay The three integrations work in concert: Integration 1: Spot Purchase Orders — D365 F&O to Legacy Business Problem A Spot Purchase Order is an ad-hoc purchase order raised outside of long-term contracts — often for urgent material procurement. Spot POs are created and managed in D365 F&O by procurement teams. However, the legacy system is the system of financial record, meaning every Spot PO created in D365 must be reflected in the legacy system for financial commitment tracking and vendor payment processing. Without integration, this would require manual re-entry – a process prone to error, delay, and duplication. How the Integration Works Parent Logic App – Spot PO Orchestrator The primary Logic App runs on a scheduled recurrence and uses a checkpoint mechanism stored in Azure Blob Storage to fetch only incremental changes – purchase orders created or modified since the last successful run. This ensures efficiency and prevents reprocessing of already-handled records. The workflow determines the operation type required for each PO: For each scenario, the Logic App fetches enriched data from multiple D365 F&O OData entities and constructs a structured JSON payload tailored for the legacy system’s API. ⚙ Tech Note: OData Entities Used PurchaseOrderHeaders, PurchaseOrderLinesV2, PurchaseLineDataEntities, WHSPurchLines, StatusCustomDatas Child Logic App – SendRequest (Reusable) Rather than embedding API communication logic directly in the orchestrator, we separated it into a reusable child Logic App. This child app receives the constructed payload, retrieves an OAuth 2.0 Bearer token, and executes the HTTP POST call to the legacy system’s API endpoint. This modular design pays dividends during maintenance: any change to authentication logic or API communication is made once in the child app and automatically applies to all parent integrations. Failed Record Handler Every enterprise integration needs robust failure recovery. When an API call fails: Sample Payload – Spot PO Create Sample JSON Payload: {   “userId”: “JSMITH”,   “order”: “456789”,   // Last 6 digits of D365 PO number   “vendor”: “VEND001”,   “receiptLoc”: “SITE01”,   “vendorOvrdCd”: “14”,   “lineItems”: [{     “orderLine”: “001”,     “item”: “ITEM001”,     “openQty”: 10,     “deliveryDate”: “061526”,  // MMddyy format for legacy compatibility     “comment”: “MPSSYS order – JSMITH” }] } } ✓ Business Impact: Zero manual re-entry of purchase orders between systems. Every Spot PO created or changed in D365 F&O is automatically reflected in the legacy system within minutes. Integration 2: Advance Shipment Notices — Legacy to D365 F&O Business Problem An Advance Shipment Notice (ASN) is a notification sent by the legacy WMS to the receiving system, informing it of an incoming shipment before it physically arrives. D365 F&O needs to receive ASNs to create Inbound Load Headers and Load Lines – enabling warehouse teams to prepare for receiving. Without this integration, receiving teams in D365 would be blind to incoming shipments until trucks arrived at the dock – eliminating any opportunity for advance dock scheduling, labor planning, or inventory pre-positioning. The Hybrid Integration Approach This integration presented an interesting technical challenge: the standard D365 F&O Inbound ASN V5 API supports a well-defined XML format, but the business required additional fields beyond what the standard API supports. The solution was a two-step Hybrid ASN Integration approach: ⚙ Tech Note: API Endpoint Pattern Insert:  POST {{BASE_URL}}/api/connector/enqueue/{{ACTIVITY_ID}}?entity=Inbound ASN V5 Enrich:  PATCH on InboundLoadHeaders and WHSASNWorkData Smart Insert vs. Update Determination To handle scenarios where an ASN might be re-sent for corrections or resynchronization, the integration includes a check before processing: This idempotent design prevents duplicate inbound loads from being created when the legacy system re-sends an ASN. One nuance worth noting: in D365’s standard ASN structure, the LoadId, ShipmentId, and LicensePlateNumber must carry the same value. The legacy system’s outbound ASN payload is configured to honour this requirement – ensuring clean data entry … Continue reading How a Top North American Commercial Vehicle Manufacturer Connected D365 F&O with Legacy Systems Without Disrupting Operations →